Calling setZoomed/setOrigin during render (inside the if (prevLibRef.current !== selectedLibrary) block) triggers state updates while rendering, which can cause render loops / React warnings (especially in StrictMode) and makes the component harder to reason about. Move this reset into a useEffect watching selectedLibrary, or derive zoomed/origin from selectedLibrary via state keyed by library.

setExpanded(false) is executed during render when specId changes. Updating state while rendering can trigger React warnings and unpredictable render behavior. Reset expanded in a useEffect on specId (or keep expanded in a key-scoped state) instead of calling the setter during render.

The zoom toggle uses setTimeout(() => setAnimating(false), 300) without cleanup. If the user navigates away quickly, this can call setState on an unmounted component (React warning) and can stack multiple timers on rapid toggles. Store the timeout id in a ref and clear it in a cleanup effect, or use requestAnimationFrame/CSS transition end callbacks.

The main image container is clickable (zoom in/out) but isn't keyboard-accessible (no tabIndex, no role="button", no key handlers) and doesn't expose an accessible name. This makes the new zoom interaction inaccessible to keyboard/screen-reader users. Consider adding a dedicated zoom IconButton (preferred) or making the container focusable with proper role, aria-label, and Enter/Space handling.

The global tag counts fetch runs in an effect but doesn't guard against setting state after unmount (no AbortController / cancelled flag). If the user navigates away before the request resolves, setTagCounts can fire on an unmounted component. Add a cancellation flag or AbortController and check it before calling setTagCounts.

The dismiss (close) IconButton is missing an aria-label, so screen readers won't announce its purpose. Add an aria-label like "Dismiss plot of the day" (or equivalent).

This note says highlight colors are "not tokenized" and intentionally kept as direct values, but the theme now exposes colors.highlight and colors.tooltipLight tokens. Update this guidance to match the actual theme API so contributors don't reintroduce hardcoded values.

The click handlers on the action IconButtons call blur() unconditionally. This removes focus even for keyboard activation (Enter/Space), which can make keyboard navigation confusing and reduces visible focus indication. Prefer relying on :focus-visible styling (already used elsewhere) or only blurring on pointer/mouse interactions.

The action button click handlers call blur() before invoking onCopyCode/onDownload. This also fires for keyboard activation, causing focus to be lost unexpectedly. Consider removing the manual blur and instead using :focus-visible styling to avoid mouse focus rings while keeping keyboard focus behavior accessible.

The UI falls back to hardcoding Python 3.13 when python_version is missing. That can display an incorrect version (and conflicts with the goal of showing real versions from the API). Consider showing an explicit "unknown"/omitting the version when null, similar to the library_version !== 'unknown' handling.